EVE Search - Socket Closed

Check My IP Information

All Channels

Issues, Workarounds & Localization

Socket Closed

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]


Author	Thread Statistics \| Show CCP posts - 8 post(s)
PaddyPaddy Nihildarnik Gallente aurorae pacificas	Posted - 2009.02.15 05:04:00 - [1] Long term player- absolutely minimal tech knowledge checking in! Because I dont have much technical know-how could someone who does please compress the info in the last 15 pages into something remotely manageable for us morons out there. So far this is what ive got from the 3+ months of this bug... Description/ Summary of Problems # Eve will crash at seemingly random occasions for some people, right from logging in (authentication>>char selection) through to simply being afk in space? # Personally I find that Eve can and will sometimes run for hours without crashing BUT when it does crash the crashes are frequent and sustained (such as 7-10 log in attempts before finally logging in) # Several error messages appear ranging from "Connection to server was closed" to "Socket connection was closed" (paraphrased!). Ive also been getting "the transport was unable to complete and connection was closed" or something like that- the message displays briefly before eve crashes back to login screen. # Multiple occasions the crashes lead to Blue Screen crashes requiring hard resets # Settings are generally lost on these hard resets- but remain on the normal crashes. # Personally my crashes seem to happen during session changes (gate jumps, docking/undocking opening market info/ changing item info on market, logging in, opening eve-mail and using show info etc) but others have stated its completely random. # Problem only began with QR patch- prior to this no problems with connectivity (beyond the normal/expected d/cs or lag induced de-syncs etc) occuring Possible Fixes (or non-fixes from my experience) 1. Re-installing fresh client/ Fresh d/l of client WILL NOT FIX THIS PROBLEM 2. Possibly changing the port/socket that Eve uses has been suggested (NEED FEEDBACK HERE- DOES THIS WORK???) 3. Contacting ISP and inquiring about possible packet-loss/ doing pingplotting or tracing the connection commonly shows packet loss/ connection drop 4. Something about the bottleneck/ Packet loss connected to Level3 isp/server?? (Please confirm???) 5. Others have simply waited it out and eve has returned to normal (not a good suggestion nor one that has worked for me) 6. Log reports are/are not useful (Please confirm) I hope that helps but a more indepth summery would be nice from anyone who knows more about this then me please... Im dying here with these connection drops
PaddyPaddy Nihildarnik Gallente aurorae pacificas	Posted - 2009.02.15 06:55:00 - [2] 13. Apparently openning high volume chat helps stop the D/c once you can log in. Open up a high volume chat such as the Help channel. Not a great fix but worth a mention... 14. Hawktt post 289 provides info regarding how packets are constructed and sent via ISPs and the Eve server (I think... again over my head ) From what I gather he is suggesting that high volume ISPs use a type of technology that can/is incomparable with the way the eve client sends packets over the net. (Again correct this info if wrong) 15. Nestor on post 331 suggests another program to help optimise connection settings. 16. Suggestions have been made that when the client crashes back to login screen, close the client completely before attempting a relog as more often then not, your connection/ socket will close. 17. Post 381 suggests possible conflict with Dell software. 18. Post 386 offers another connectivity solution. 19. Post 397 offers link to CCP port changes from 26000 but as mentioned before this has been shown to not work for most players. OK guys thats ALL the relevant info from Page 1- now. If you are continuing to have problems DO NOT CLUTTER THIS THREAD WITH RAGE QUIT THREATS. If you must threadnought the GD forum. * DO NOT POST GM CHATS- mods are deleting them anyway. It will not accelerate a fix. * Actually try any/all the above approaches and IF THEY WORK LET US KNOW. Even if its a shtty temp fix it might narrow down the problem for CCP. Continue running/filing bug reports ping plotting. From the data in this thread I am concluding the following 1) 90% of eve are emo-raging children. 10% are actively trying to fix this and should be commended. 2) The problem more then likely was developed out of the QR patch, possibly in the Exe file. It is adversely affecting connections via routers or more likely through packet distribution. 3) Several servers in the later stages (hops?) just before info gets to the Eve server appear to be having difficulty in processing eve related packets. These are located in London, apparently. 4) Therefore client type, isp, OS and connection type are probably not the root cause of the problem but may contribute to it. 5) Third party programs may help streamline or remove the problem as a stopgap fix. 6) Diverting away from the afor mentioned servers might fix this but I dont know how to do this or if its even possible. 7) CCP are aware of the problem- continue applying pressure to make sure this is a high priority for them until they actually come on here and state in bold that it is their biggest priority! Phew- hope that helps fellas. Find me a fix plsthxbye.
PaddyPaddy Nihildarnik Gallente aurorae pacificas	Posted - 2009.02.19 07:16:00 - [3] Originally by: Cyclicus Remba I got dropped 3 times with 25 minutes, then tried this and have been fine since (3+ hours). Of course, there's no way for me to verify that this program helps at all, but meh, I'll use it till my "luck" runs out. Sometimes I'll get socketed 3 times in an hour, sometimes once in 3 hours, sometimes not for 5 hours. Still doesn't change the fact that the hop before the server is essentially dead, regardless of how long pingplotter is running. Maybe I'll try it while wearing a pink carnation, pasties and wingtips while humming Marche Slave. It just might work! I'll let you know how it goes. FFS, how about actually trying to give some useful feedback rather then clogging up this thread with more useless whining. GD forums ------------> that way. For everyone else not wanting to read 16 pages of to and fro I made a summary of this thread on page 15. # GO THERE FIRST BEFORE WHINING AND COMPLAINING. # TRY THE OPINIONS THERE FIRST BEFORE WHINING AND COMPLAINING. # THIS PROBLEM IS ****TY ENOUGH WITHOUT YOU ADDING TO IT. KEEP THE THREAD CLEAN
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.02.21 17:03:00 - [4] Bumping this for yet another 100mil+ loss due to the client d/cing me.
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.02.22 04:21:00 - [5] Target Name: N/A IP: 87.237.38.200 Date/Time: 22/02/2009 2:40:13 PM to 22/02/2009 3:20:10 PM Hop Sent Err PL% Min Max Avg Host Name / [IP] 1 961 24 2.5 8 98 13 [10.23.64.1] 2 961 24 2.5 9 165 13 sbr4-pos4-0-1.gw.optusnet.com.au [198.142.144.117] 3 961 24 2.5 10 141 14 mas1-ge11-0-5-900.gw.optusnet.com.au [198.142.144.194] 4 961 24 2.5 10 112 14 mas3-ge2-0-0-811.gw.optusnet.com.au [211.29.155.11] 5 961 24 2.5 170 261 176 [203.208.148.97] 6 961 24 2.5 169 294 175 ge-0-0-0-0.laxow-dr1.ix.singtel.com [203.208.171.65] 7 494 24 4.9 171 594 184 ge9-10.br01.lax05.pccwbtn.net [63.218.73.101] 8 961 271 28.2 314 740 332 telecity.ge9-9.br02.ldn01.pccwbtn.net [63.218.13.222] 9 961 24 2.5 314 523 322 mailtx.2zxr.com [217.20.44.10] 10 960 960 100.0 0 0 0 [-] 11 961 24 2.5 315 395 320 [87.237.38.200] Ive bolded the anomolies in my pingplotting. Why is the 10th hop 0? Is that due to total packet loss?
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.02.23 12:50:00 - [6] After running pingplotter @ 15000 traces or whatever and running trace every 1 seconds I have noticed a definite reduction in crashes. Dont understand the mechanic of it and its not guarenteed solution, merely a bandaid. Still, id highly recommend it to everyone.
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.02.23 16:15:00 - [7] Edited by: PaddyPaddy Nihildarnik on 23/02/2009 16:15:16 Originally by: Nean Derthal I finally ran the pingplotter and this is what came out Target Name: N/A IP: 87.237.38.200 Date/Time: 23-02-2009 13:56:48 to 23-02-2009 14:20:42 Hop Sent Err PL% Min Max Avg Host Name / [IP] 1 1433 0 0,0 0 11 1 [192.168.2.1] 2 1433 0 0,0 5 99 14 [10.11.191.254] 3 1433 2 0,1 5 93 15 a212-113-169-254.netcabo.pt [212.113.169.254] 4 1432 147 10,3 12 85 21 ix-4-0-0.core1.PV9-Lisbon.as6453.net [195.219.187.34] 5 1433 1 0,1 12 79 20 if-4-0-0.core1.PV9-Lisbon.as6453.net [195.219.187.33] 6 1433 1 0,1 39 262 55 if-12-0-0.mcore3.L78-London.as6453.net [195.219.144.5] 7 1433 0 0,0 39 91 48 if-5-0-0.mcore3.LDN-London.as6453.net [195.219.195.9] 8 1433 0 0,0 39 304 70 ldn-b4-link.telia.net [213.248.74.1] 9 1433 2 0,1 39 490 69 ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.90.90] 10 1431 650 45,4 40 119 59 [87.237.38.200] I dont understand anything of it though From hop 6 you are getting around 40% packet loss. This result is different to others who has posted though by the looks of it. Try running the log server and submitting a petition to ccp bout it. Your problem might/might not be the same as everyone else in this thread. I cant really say either way. Hop 7 hits a london server though... thoughts anyone?
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.02.27 06:14:00 - [8] Originally by: Moonaru Izu Edited by: Moonaru Izu on 26/02/2009 13:07:47 Originally by: Kayl Breinhar Edited by: Kayl Breinhar on 26/02/2009 11:40:03 Contacted Telecity Group myself, they got back to me within 20 minutes and an hour, which is impressive. Turns out the offending hop belongs to PCCW, and it's a router they own. The use of "telecity" in the server address is because the router is housed in one of their datacenters. The reply: "That is a pccw router. I imagine its called telecity because its in one of our sites but if you check out the dns name you'll see pccwbtn.net which should lead you to its owner!" Actually it seems to be owned by a subsidiary of PCCW called BTNAccess. See this website and how the last part of the domain matches the server. http://peering.pccwbtn.net/index.html Also, you can see they are US based (or at least have an office there) and even have a phonenumber and email adresses for technical support. I already wrote an email to the non-US support office but no reply yet. Maybe one of you located in the USA could give these guys a call? Top notch effort on that one. Please one of you US guys get a hold of this company and get the ball rolling. Hell ask em to contact ccp to confirm at least :(
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.02.27 13:27:00 - [9] Originally by: Kappas. Removing vista and reinstalling xp solved this problem for me, so i'm assuming it's a problem somewhere in vista for a lot of people. Quoting someone who has not read a bloody single post beyond the OP.
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.03.01 12:23:00 - [10] Im hoping this gives us something of a response.

PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.03.02 09:38:00 - [11] Originally by: Grall Sek Telecity its not the only problem, my connection doesnt use telecity router and still i get disconnected alot. Please post you pingplotter results. It could be that your problem is not related to the one mentioned in this thread.
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.03.06 16:28:00 - [12] Originally by: Kyguard Originally by: PaddyPaddy Nihildarnik After running pingplotter @ 15000 traces or whatever and running trace every 1 seconds I have noticed a definite reduction in crashes. Dont understand the mechanic of it and its not guarenteed solution, merely a bandaid. Still, id highly recommend it to everyone. How did you set this up? Its fairly easy. 1) Open Pingplotter 2) In the bottom Left there are several value boxes under the heading "samples" 3) Change "# of times to trace" to a high number, like 15000. This means literally how many times ping plotter will "ping" whatever addy you put into it to trace. 4)Change "trace interval" to 1 sec. This means that pingplotter will "ping" every second. 5) Type in eve server addy ( 87.237.38.200) 6) Hit trace and leave running in the background. More info on page 4 or 5 I think where a GM links the pingplotter website. If you are having this issue then as stated, this may/may not bandaid it for the time being.
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.03.22 07:35:00 - [13] Ok this post will probably get deleted. I have been in a too and fro with GMs about this for some time now and they are adamant that it is NOT ccp's problem. Basically they tentatively confirmed that it has something to do with the individual isp's routes going through that common server hop. Now im not a tech head so forgive the incorrect word usage- I just hope the other laymen out there understand what im saying. Ive been having the problem since the QR patch. IMO something in the way eve communicates with these server hops has caused the problem- perhaps its an issue from the isps not accepting or prioritizing the packets correctly, I simply dont know. What I do know is that CCP will NOT be helping with this. Ive had 2 seperate GMs confirm they (CCP devs) specifically know about the issue. Ive also asked both to mention to whoever it may be that is in charge of the problem solving for this issue to post in this thread- even a simple "hey guys we know about it and are doing our best etc". They both said they have passed the message on. Given that there is no reply as yet I can only assume CCP doesnt give a flying f-ck about the issue. Either its a too hard basket or a couldnt be assed basket. Either way we are on our own. As far as CCP is concerned- they couldnt help anyway so why bother replying. Also dont bother petitioning or submitting bug reports or server logs about this or about lost ship reimbursement due to this. They have refused several of mine, dont bother clogging up the already clogged system. The only advice I can offer is.. 1) Running ping plotter seems to help keep connected some of the time. 2) Restart client when you crash back to log in screen. Much better chance of reconnect- dont know why. 3) Contact your isp and try to get re-routed around that particular hop. Have pingplotter results handy. These will have the servers details in it. Hopefully your ISP isnt a complete **** and will help you out. Im trying with mine tomorrow. 4) If your ISP doesnt help go shop for another one who is prepared to re-route your connection or resign yourself to this existence. As absolutely shiity as it isCCP will NOT be helping out anymore on this issue. 5) Others have mentioned programs that re-route you. I havnt tried these as im pretty keen on a new isp anyway but give that a go. Re-read the thread and garner as much info as possible. Other then that you are on your own, unfortunately.
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.03.26 03:00:00 - [14] Edited by: PaddyPaddy Nihildarnik on 26/03/2009 03:00:59 Originally by: shifty one It's quite normal to see packetloss at certain hops in Pingplotter. That is just happening because those servers are not responding to the requests made by Pingplotter. However, unless you also see packetloss at every hop after that, all the way to the last hop, then all the packets are reaching the final destination and the hop that reported the packetloss is not an issue. Therefore the packetloss reported at telecity-redbus-gw1.ip.tiscali.net is not relevant unless it were to continue reporting packetloss through the last hop. Please keep in mind that there are also thousands of people going through that hop and experiencing no problems. We are still trying to find the source of this issue and that is being worked on with high priority. this is in exact contrast to the info I recieved. Who to believe????? Clearly CCP dont know what the problem is. Is it a server side issue? A client side issue? An ISP issue? From the above it could be any This is just beyond incompetent. I know it seems pointless but I have advised several of my friends who were previously interested in Eve to not bother. I know 4-8 accounts seems like a drop in the ocean but there are probably what, 200 or more individual chars posting in this thread. If you all make an effort to do the same thats 1000 accounts ccp will no longer be getting. Would 15k/mth less income be significant enough for a Dev to get off his/her ass and post something in this thread? Ive seen them posting inane useless shiit on GD, so its not a "we're too busy" issue, its a "couldn't care less issue". BTW the petition I had running was simply closed/deleted. I didnt even get the "are you happy we close this?" reply...
PaddyPaddy Nihildarnik Gallente H A V O C Minor Threat.	Posted - 2009.03.27 09:42:00 - [15] Edited by: PaddyPaddy Nihildarnik on 27/03/2009 09:43:27 I had an eve mail sent to me today from a trial account who couldnt post on this forum who is having this exact issue happening too. 2009.03.26 20:16 Hi Paddy, I've just read your post on Eve 'Player Exclusive' Forums concerning the 'socket closed' issue .... I couldn't find a way to post inside this topic (i'm using the trial version), but definitely agree with you about this : Originally by: 'paddy' "there are probably what, 200 or more individual chars posting in this thread. If you all make an effort to do the same thats 1000 accounts ccp will no longer be getting." Do they really believe they'll get new customers to pay for playing in those conditions ? There's no way I'll upgrade my account if they don't fix things up soon. Said it all :) Feel free to post this as a ''201st-or-so unhappy player notice", if you happen to get bored between two sockets closing... or just to correct my weird english, guess I could use some lessons :) anyway, have a nice playing session, maybe we'll meet around someday :) Ciao ! Sigisoarah Kinda sad that this is the introduction to Eve that potential new players are getting. For a problem so endemic, so widespread I am simply lost for a reason that CCP wont reply to this forum. I stand by my previous statements. I have long supported CCP, gave em free PR, raved about it to friends, defended their sometimes shady in-game actions. All this ends now until this conflict is resolved. Im doing my best to spread awareness of this amongst the Eve community too, for what they might care. CCP, you are giving your clients such a bum steer dont be surprised when your subs drop when the first real mmo competition you get comes out. Wake up and smell the aweful job you have done handling this...

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.